Ensuring the performance of mandated inspections combined with the collection of ancillary data

ABSTRACT

During an inspection discrete checkpoints provide data to a portable reader, enabling a record to be generated identifying each checkpoint visited during an inspection. At least one checkpoint associated with the inspection will convey ancillary data to the portable device, either in lieu of, or in addition to, a checkpoint ID uniquely identifying a location or component inspected. The ID is not ancillary data, because the only function of the ID is to verify that an inspector was present at a particular location or component. In contrast, ancillary data are data that have an additional utility. For example, a sensor may be disposed in proximity of the component or location to be inspected. Data collected by such a sensor represents ancillary data, because such data does more than uniquely identify a particular location or component that was visited during an inspection.

RELATED APPLICATIONS

This application is a continuation-in-part of prior co-pendingapplication Ser. No. 10/915,957, filed on Aug. 11, 2004, which itself isa continuation-in-part of prior co-pending application Ser. No.10/219,892, filed on Aug. 15, 2002 and now issued as U.S. Pat. No.6,804,626 on Oct. 12, 2004, which itself is a continuation-in-part ofprior application Ser. No. 09/951,104, filed on Sep. 11, 2001 and nowissued as U.S. Pat. No. 6,671,646 on Dec. 30, 2003, the benefit of thefiling dates of which is hereby claimed under 35 U.S.C. § 120.

BACKGROUND

Mandated inspections are required in a variety of different contexts.For example, to avoid accidents caused by defective equipment, Federallaw presently requires that commercial drivers make a visual inspectionof specific components on a commercial vehicle such as a truck (i.e.,tractor and trailer), including components such as the brake system,fuel system, warning lights, tires, etc., performing pre- and post-tripinspections of these basic, but critical components. An exemplaryvehicle inspection report, listing the components and systems that mustbe inspected by a driver to satisfy the DOT regulations, is illustratedin FIG. 7. However, under the current system, a driver is only requiredto fill out a paper log and keep it on file for 90 days. Many expertsreport that less than half of the drivers ever perform the check;instead, many drivers simply fill out the report while seated in the cabof the truck or in a coffee shop. The report is meaningless unless thelisted components and systems have actually been inspected. For example,a driver who fails to actually inspect components on his vehicle willnot notice that brake fluid is leaking from a hydraulic master brakecylinder. As a result, the brakes on the driver's truck may fail,potentially causing a serious accident.

Unfortunately, a signed inspection report does not provide any assurancethat a driver actually inspected the components included on the report,because the individual tasked with performing the inspection couldsimply sit in a comfortable location, such as the cab of the vehicle,and complete the inspection report without actually physically beingpresent at the locations requiring inspection. Thus, it would bedesirable to provide a way to verify that the person tasked withperforming an inspection actually was present at the location requiringinspection.

SUMMARY

One concept described in detail below relates to automatic collection ofancillary data during an inspection. The term “ancillary data” isintended to refer to data that does more than simply verify that aninspector was present at a particular location, checkpoint, or componentduring an inspection, and might, for example, include data correspondingto values of parameters collected during the inspection.

A related concept, also described herein, is directed to a method forgenerating a record indicating that a component of a vehicle, or othertype of apparatus or system, or a specific location, was visited duringan inspection. Such a method employs a portable device for use inrecording data related to the inspection. The portable device includes asensor that produces a signal indicative that an operator has positionedthe portable device proximate a component/location. A record of thesignal produced by the sensor is made and is stored within the portabledevice, providing evidence that the operator was sufficiently close tothe component to make an inspection of the component. Preferably, eachdifferent component or location visited during an inspection willprovide a different signal to the portable device, such that the recordgenerated by the portable device can be used to identify thelocations/components that were inspected, and the locations/componentsthat may have been inadvertently omitted from the inspection. Onetechnique for implementing this method involves providing a token ateach location/component, where the token conveys a unique tokenidentification (ID) to the portable device when the portable device isproximate the token.

With respect to the method of collecting ancillary data during aninspection described in detail herein, at least one such token willconvey ancillary data to the portable device, either in lieu of, or inaddition to, a token ID uniquely identifying a location or component.Note that the token ID itself is not ancillary data, because the onlyfunction of the token ID is to verify that an inspector was present at aparticular location or component associated with the token ID. Incontrast, ancillary data are intended to represent data that have anadditional utility. For example, a sensor may be disposed in proximityto the component or location to be inspected. Data collected by such asensor represents ancillary data, because such data does more thanuniquely identify a particular location or component that was visitedduring an inspection. In accord with one exemplary embodiment, during aninspection, ancillary data will be collected from at least one locationor component during the inspection.

This Summary has been provided to introduce a few concepts in asimplified form that are further described in detail below in theDescription. However, this Summary is not intended to identify key oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

DRAWINGS

Various aspects and attendant advantages of one or more exemplaryembodiments and modifications thereto will become more readilyappreciated as the same becomes better understood by reference to thefollowing detailed description, when taken in conjunction with theaccompanying drawings, wherein:

FIG. 1 is a schematic diagram of a tractor and trailer equipped withtokens at each component to be inspected, illustrating a person using aportable device in accord with the present invention;

FIG. 2 is a top plan view of a portable device for use in making asafety inspection of a tractor and trailer, showing a message thatprompts the operator to inspect the left rear tires of the tractor;

FIG. 3 is a schematic block diagram of the functional componentsincluded in the portable device of FIG. 2;

FIG. 4 is a top plan view of the portable device of FIG. 2, illustratinga menu that indicates possible conditions of tires in need of service;

FIG. 5 is a flow chart showing the steps followed in carrying out asafety inspection in accord with the present invention;

FIG. 6 is a flow chart illustrating the steps employed in recording acondition of a component that is being inspected using the portabledevice of FIGS. 2 and 4;

FIG. 7 (Prior Art) is an exemplary manually-completed inspection recordused for safety inspections of tractors and trailers, illustrating thespecific components and systems that are required to be inspected;

FIG. 8 is an exploded isometric view of a portion of a second embodimentof the portable device that includes a plurality of lights;

FIG. 9 is an isometric view of a front portion and lower surface of thesecond embodiment of FIG. 8;

FIG. 10 is an isometric view of the lower surface of a third embodimentof the portable device that includes a digital camera;

FIG. 11 is an isometric view of the upper surface of either the secondor third embodiments;

FIG. 12 is a flow chart illustrating the steps implemented during asafety inspection in which the user has an option to record a digitalimage of a component being inspected;

FIG. 13 is a side elevational view of a bus, illustrating thedisposition of a token adjacent to a rear of the bus that is scanned toensure that a driver of the bus has inspected all of the seats todetermine whether all passengers have been unloaded from the bus;

FIG. 14 is an isometric view of a docking station for the portabledevice;

FIG. 15 is an isometric view of the second or third embodiment seatedwithin the docking station for data transfer;

FIG. 16 is a schematic diagram of the system for transferring data overthe Internet, between the portable device in the docking station andstorage on a remote server;

FIG. 17A is a schematic block diagram indicating three different typesof data that can be collected by the portable device in accord with yetanother embodiment described herein;

FIG. 17B is a schematic block diagram of a sensor configured to collectancillary data logically coupled to a token, thereby enabling theportable device to automatically collect ancillary data during aninspection;

FIG. 17C is a schematic block diagram of a sensor configured to collectancillary data and to communicate with the portable devices describedherein, thereby enabling the portable devices to automatically collectancillary data during an inspection;

FIG. 18 schematically illustrates a public transport vehicle configuredto enable the portable devices described herein to automatically collectinspection data and ancillary data, contemporaneously with aninspection;

FIG. 19 schematically illustrates an exemplary token configured toconvey ancillary data to a portable device; and

FIG. 20 is a flow chart illustrating the steps employed incontemporaneously collecting inspection data and ancillary data.

DESCRIPTION

Figures and Disclosed Embodiments Are Not Limiting

Exemplary embodiments are illustrated in referenced Figures of thedrawings. It is intended that the embodiments and Figures disclosedherein are to be considered illustrative rather than restrictive.

Utility of the Various Exemplary Embodiments Described Herein

The present concept disclosed herein is applicable to recording dataresulting from an inspection of almost any type of vehicle, equipment,apparatus, or system, and is particularly applicable to inspections inwhich it is desirable to maintain a data record as evidence that theperson making the inspection was actually physically present at acheckpoint, location, or component requiring inspection. While the dataaccumulated using the present concept is not conclusively presumptiveevidence that each location or component to be inspected was indeedcarefully inspected, in most cases, if a person is required to visit alocation or component, it is very likely that the person will actuallyinspect the location or component. By encouraging a person making aninspection to be physically close enough to a particular location orcomponent to carry out an inspection, and by providing evidence of thatfact in the data recorded, there is at least a justifiable presumptionthat the person actually performed the inspection.

It should be recognized that while a portion of the following disclosureis specifically directed to the pre-trip inspection of commercialvehicles, that such an inspection is intended to be exemplary, ratherthan limiting the inventive concept disclosed herein. In particular, thecontemporaneous collection of ancillary data during an inspection willbe discussed in detail below, and such ancillary data can be collectedduring any type of inspection, regardless of whether the inspection isrelated to a vehicle, or related to a safety inspection.

A majority of the present disclosure refers to the inspection of acomponent. In many cases, particularly with respect to the pre-tripinspection described in detail below, specific components (such as avehicle lights, vehicle brake systems, vehicle tires, etc.) are beinginspected. In other inspections, rather than a specific component beinginspected, the purpose of the inspection is to check a general location.For example, the terrorist threat to public transportation may prompt arequirement that all passenger vehicles (such as trains, buses, andairplanes) be regularly inspected. Rather than indicating that specificcomponents of the vehicle need to be inspected, an inspection directedto minimizing a terrorist threat will likely involve checking thoseportions of the vehicle that can be accessed by passengers, to ensurethat no passenger has left behind a potentially dangerous device, suchas an explosive or toxin. This may involve thoroughly inspectinglocations such as restrooms, galleys, seating areas, overhead storagebins, and other areas that can be accessed by passengers during transit.In this case, the inventive concept described herein can be used toverify that an inspector was present at a series of predefined locationsassociated with a particular vehicle. Thus, it should be understood thatan inspection can involve a specific component (such as a vehicle tire),a predefined checkpoint (such as each door in a transit or otherfacility), or a particular location (such as the seating area andluggage bins in a transportation vehicle).

FIG. 1 illustrates a tractor-trailer 10 with which an embodiment of thepresent invention is usable to carry out a safety inspection.Tractor-trailer 10 is provided with a plurality of tokens affixedadjacent to each checkpoint or component that is to be inspected. Whileonly a few of the tokens are illustrated in FIG. 1, FIG. 7 (Prior Art)lists all of the components or systems that should be inspected if adriver is to be in compliance with the DOT regulations regarding pre-and post-inspections of such vehicles. A token will preferably beaffixed adjacent to the components and systems listed in FIG. 7,although several components might be associated with the same token. Forexample, in the engine compartment, one token might be used for both theradiator and the belts. As a driver moves about the tractor and trailer,evidence that the driver or the person doing the inspection movedsufficiently close to the components being inspected so that theinspection could actually take place is recorded in a portable device 20(first embodiment). Further details of portable device 20 and of otherrelated embodiments are described below.

For the few tokens illustrated in FIG. 1, the relevance of thedisposition of the token adjacent to a corresponding component of thetractor-trailer 10 should be evident. For example, token 12 is disposedadjacent to tandem dual rear tires 14 on the trailer. Since all thetires of the tandem dual rear wheels on the left rear of the trailer arereadily visible from a position adjacent to token 12, a single token issufficient to determine that the driver was sufficiently close so thatall four tires at the left rear of the trailer could be readilyinspected. Similarly, tandem dual wheels 18 on the left rear of thetractor are readily inspected when an observer 22 is positioned as shownin FIG. 1. In this position, the observer moves portable device 20within a maximum predefined range of token 16, which is exposed abovetandem dual wheels 18. Portable device 20, detects and responds to token16, recording data indicating that the driver was in a position toinspect tandem dual rear wheels 18 on the tractor. It is contemplatedthat the operator may initiate the recognition of a token by activatinga switch, or the portable device can instead simply respond when a tokenis sufficiently close to the portable device.

Other tokens 24, 26, 30, and 32 are illustrated adjacent othercomponents of the tractor that are part of the safety inspection. Forexample, token 26 is affixed adjacent a tire 28 on the right front ofthe tractor, while tokens 30 and 32 are accessible if the front hood ofthe tractor is opened and are disposed adjacent the hydraulic brakemaster cylinder and the engine belts/radiator, respectively (not shownseparately).

For each token there is a predetermined maximum distance that portabledevice 20 can be held from the token that will enable the portabledevice to detect the token, and thus, the component that is associatedwith it in order to produce a record as evidence that the person holdingthe portable device was in a position to inspect the component.Depending upon the component to be inspected and the type of token,different predetermined maximum distances may be assigned to the variouscomponents. The different predetermined maximum distances might beimplemented by partially shielding a token to vary the distance at whichthe portable device can detect the token.

Operator 22 is prompted to approach the next component in a series ofcomponents that must be checked during the safety inspection by amessage 58 appearing on a display 40 of portable device 20, as shown inFIG. 2. For example, if operator 22 has just completed the inspection oftandem dual tires 14 on the left rear of the truck, display 40 providesa prompt 58 indicating that the operator should “verify tirecondition—left rear of tractor.” A sensor 46 on portable device 20responds to token 16 when the portable device is held less than thepredetermined maximum distance from token 16 by producing a signalindicating that the portable device was within the required range oftandem dual tires 18 to enable the operator to inspect the tires.Display 40 also provides a prompt 60 to operator 22 requesting that theoperator indicate whether the tire condition is okay. If so, theoperator presses a green control button 52 corresponding to the message“YES, OK.” However, in this first embodiment of the portable device, ifduring the visual inspection of the tires the operator determines thatthey require servicing, the operator is prompted to depress a yellowcontrol button 54 on the portable device. (The other embodiments of theportable device that are described below do not include a yellow controlbutton, but instead invite the operator to indicate the condition of thecomponent.)

Certain conditions such as a tread separation or a nail or other sharpobject lodged in the tire would likely lead the person doing theinspection to depress a red control button 56, indicating a safetyproblem that requires the operator to refer to a supervisor who willlikely elect to delay the trip until the tire is repaired and/orreplaced or take other appropriate action depending upon the nature ofthe component and the type of problem that makes the component unsafe touse. Portable device 20 also includes a cursor control 50, which is afour-position switch that enables a cursor (not shown in this Figure) tobe moved up or down, and left or right. Cursor control 50, green,yellow, and red control buttons 52, 54, and 56 (respectively), anddisplay 40 are all disposed on a front surface of a housing 42 ofportable device 20. Sensor 46 is disposed on the top edge of housing 42,while an optional universal serial bus (USB) port 48 is disposed on thebottom edge of housing 42, opposite from sensor 46.

In this embodiment, an antenna 44 is also disposed on the top edge ofthe housing for transmitting radio frequency (RF) transmissions to aremote data storage site 61 that is used for long-term storage of dataresulting from safety inspections. The data produced by a safetyinspection indicates each of the components of the vehicle (or othersystem or apparatus being inspected) that were visited by the operator,so that the portable device was positioned within the predeterminedmaximum distance from the token associated with the component, andfurther indicates the status of the component. In the event that thecomponent appears to need service or represents a safety problem (aswould be evident if the operator depressed yellow control button 54 orred control button 56, respectively), the operator is prompted to selectone of a plurality of predefined conditions that justify the state ofthe component determined by the operator and best represent its observedcondition.

If the state of the component is okay and green control button 52 isdepressed (i.e., if the component does not require any service and isusable or otherwise within its nominal operating parameters), there isno need to provide an indication of the condition of the component. Thecondition need only be recorded as part of the data stored in theportable device if either yellow control button 54 or red control button56 is depressed by the operator to indicate the state of the componentbeing other than “OK.”

A further example, illustrating the selection of a condition relating tothe example shown in FIG. 2, is included in FIG. 4. As shown in FIG. 4,if the operator has indicated that the state of the tires is such thatthey need service by pressing yellow control button 54, portable device20 automatically displays several possible conditions that would haveled an operator to indicate that state. In the example shown, message 58prompts the operator to use the arrow button (i.e., cursor control 50)to select a possible condition from among the listed options that bestdescribes the observed condition of the tires. Display 40 includes fivepossible conditions, the last of which covers any condition that mightnot be included among the first four that are listed. Using cursorcontrol 50, the operator can move the cursor to the displayed statementthat best describes the observed condition of the tire and then candepress red control 56, which corresponds to an “Enter” menu option 70on display 40 for this screen. Green control 52 can be depressed toselect a “Previous” display, if the operator elects to reconsider thestate of the component that was previously selected.

FIG. 3 illustrates functional components 67 that are included inportable device 20, either on or inside housing 42. A central processingunit (CPU) 62 comprises the controller for portable device 20 and iscoupled bi-directionally to a memory 64 that includes both random accessmemory (RAM) and read only memory (ROM). Memory 64 is used for storingdata in RAM and machine instructions in ROM that control thefunctionality of CPU 62 when executed by it. CPU 62 is also coupled toreceive operator input from controls 68. Collectively, controls 68include green control button 52, yellow control button 54, red controlbutton 56, and cursor control 50. In addition, CPU 62 provides text andgraphics to display 40 for the prompts and other messages, and menuitems and options from which the operator can select using cursorcontrol 50.

After operator 22 has visited each of the checkpoints required for thesafety inspection, the operator can optionally transmit the data thathave been collected during the inspection to remote data storage site 61through an RF transmission via antenna 44. The data provides evidencethat the operator has visited the components and indicated the state andcondition of the components that were visited and inspected.Alternatively, optional USB port 48, on portable device 20, can becoupled to a network interface 63 on an external cradle or dockingstation (an example of which is described below in connection with otherembodiments of the portable device), which is in communication withremote data storage 65, as shown in FIG. 2. In FIG. 3, CPU 62 is showncommunicating data to transmitter 66 (or through another data link)using a wire and/or wireless data communication link. The data collectedand stored (in memory 64 of portable device 20) during the safetyinspection can thus be safely transferred to the remote data storagesite and retained for as long as the data might be needed.

In some cases, it may be preferable to transmit the data to the remotesite immediately after making a safety inspection to ensure that thedata retained in memory 64 are not lost should an accident occur thatdestroys portable device 20. An accident destroying the evidence thatthe safety inspection was implemented could have an adverse effectduring any litigation related to the accident, which might allegedlyhave been caused by one of the components inspected. However, since therisk of such an accident is relatively remote, it is contemplated thatan operator may collect the data from a number of safety inspections inmemory 64 and then subsequently upload the data to remote data storage65 by coupling the data to the external cradle or docking station thatincludes a USB port terminal and network interface to couple over theInternet or other network to a remote storage. The cradle or dockingstation might be maintained by a carrier at a freight terminal at leastperiodically visited by the truck that was inspected.

Alternatively, the external cradle or docking station might be disposedat a different site and/or connect to the remote data storage sitethrough other types of communication links. One example of such acommunication system is the OMNITRACS™ satellite mobile communicationsystem sold by Qualcomm Corporation that enables drivers on the road andcarriers to remain in communication with each other and enables thecarrier to monitor the location of a tractor-trailer during a trip. Bylinking portable device 20 through USB port 48 to such a datacommunication system, the data stored within memory 64 can readily betransmitted to a remote site maintained by the carrier for long-termstorage, even while a trip is in progress.

The tokens that are affixed at various points on the tractor-trailer (oradjacent components of other types of systems or apparatus unrelated toa vehicle) can be of several different types, depending upon the type ofsensor 46 that is included on portable device 20. In a preferred form ofthe present invention, the token that is preferably employed is a radiofrequency identification (RFID) tag that is attached with a fastener oran appropriate adhesive to a point on a frame or other support (notshown) adjacent to the component associated with the token. One type ofRFID tag that is suitable for this purpose is the WORLDTAG™ token thatis sold by Sokymat Corporation. This tag is excited by an RFtransmission from portable device 20 via antenna 44. In response to theexcitation energy received, the RFID tag modifies the RF energy that isreceived from antenna 44 in a manner that specifically identifies thecomponent associated with the RFID tag, and the modified signal isdetected by sensor 46.

An alternative type of token that can also be used in this invention isan IBUTTON™ computer chip, which is armored in a stainless steel housingand is readily affixed to a frame or other portion of the vehicle (orother type of apparatus or system), adjacent to the component associatedwith the IBUTTON chip. The IBUTTON chip is programmed with JAVA™instructions to provide a recognition signal when interrogated by asignal received from a nearby transmitter, such as from antenna 44 onportable device 20. The signal produced by the IBUTTON chip is receivedby sensor 46, which determines the type of component associated with atoken. This type of token is less desirable since it is more expensive,although the program instructions that it executes can provide greaterfunctionality.

Yet another type of token that might be used is an optical bar code inwhich a sequence of lines of varying width encodes light reflected fromthe bar code tag. The encoded reflected light is received by sensor 46,which is then read by an optical detector. Bar code technology is wellunderstood in the art and readily adapted for identifying a particulartype of component and location of the component on a vehicle or othersystem or apparatus. One drawback to the use of a bar code tag as atoken is that the bar code can be covered with dirt or grime that mustbe cleaned before the sequence of bar code lines can be properly read.If the bar code is applied to a plasticized adhesive strip, it canreadily be mounted to any surface and then easily cleaned with a rag orother appropriate material.

Yet another type of token usable in the present invention is a magneticstrip in which a varying magnetic flux encodes data identifying theparticular component associated with the token. Such magnetic strips areoften used in access cards that are read by readers mounted adjacent todoors or in an elevator that provides access to a building. However, inthe present invention, the magnetic flux reader comprises sensor 46 onportable device 20. The data encoded on such a token are readily read asthe portable device is brought into proximity of the varying magneticflux encoded strip comprising the token.

As yet another alternative, an active token can be employed thatconforms to the BLUETOOTH™ specification for short distance datatransfer between computing devices using an RF signal. However, it islikely that the range of the signal transmitted by the token would needto be modified so that it is substantially less than that normallyprovided by a device conforming to the BLUETOOTH specification. It isimportant that the portable device be able to detect that it isproximate to the component only within a predetermined maximum rangeselected to ensure that the operator is positioned to actually carry outan inspection of the component.

Logical Steps Implemented in the Present Invention

FIG. 5 illustrates the logical steps implemented in connection with thepresent invention to carry out a safety inspection of a vehicle or otherapparatus or system. From a start block 80, a step 82 provides formanual entry of an operator identification (ID) into a data record, orthe operator ID can already be stored in memory of the portable device,or can be automatically entered in response to a special operator ID tagdisposed on the vehicle. Cursor control 50 is employed to sequentiallyselect digits from a displayed list, to input the operator ID for theindividual making the safety inspection. The operator ID might be a four(or more) digit number or alphanumeric code. Alternatively, a pluralityof possible operator IDs might be displayed as a list on portable device20, enabling the operator to select his/her operator ID from the listusing cursor control 50 and one of the three control buttons.

Once the operator ID is entered, portable device 20 prompts the operatorto proceed to a first inspection point at a step 84. For example, asindicated in FIG. 2, message 58 prompts the operator to verify the tirecondition on the left rear of the tractor. A decision step 85 determinesif the portable device has detected the token associated with thecomponent that is next to be inspected. If not, the logic loops untilthe component is detected. Once sensor 46 on portable device 20 hasdetected the token associated with the current component to beinspected, the logic then advances to a step 86 in which the operator isprompted to indicate a state of the component (and possibly, itscondition). In a step 88, the operator performs the inspection, whichmay involve visually observing the state and condition of the component,or carrying out other steps that might be required to confirm the stateand condition of the component. It is contemplated that in some types ofinspections, a series of one or more steps might be required to test thecomponent to determine if it is operating properly, needs maintenance orrepair, or is unusable. Again, portable device 20 can be programmed toprovide appropriate prompts to direct the operator through the series ofsteps required to carry out the inspection of such a component.Accordingly, in a step 90 the operator selectively enters the conditionof the component into portable device 20 using the control buttons andcursor control 50.

A decision step 92 determines if there are further inspection points inthe safety inspection currently being carried out. If not, a step 94provides for transmitting or loading the inspection data into storage ata remote site; this step can be done immediately after the inspection iscompleted, or at some later time, perhaps after additional safetyinspections have been completed, and/or after the portable device hasbeen inserted into the external cradle or docking station. Once the dataare transmitted to the remote site for long-term storage, the process iscompleted in a step 96.

Assuming that further inspection points remain in the safety inspectionat decision step 92, a step 98 provides for the operator to proceed tothe next inspection point, which will again be determined by a promptdisplayed to the operator on display 40 of portable device 20. The logicthen loops back to decision step 85, which determines if the sensor onthe portable device has detected the component, indicating that theportable device is within the predefined maximum range of the token,thus ensuring that the operator is sufficiently close to the componentto inspect it.

Further details of step 90 are illustrated in FIG. 6. From a start block100, a decision step 102 determines if the inspected component is okay.If so, the operator presses green control button 52 in a step 104. Sincethe component is okay, nothing further is required for that component,and the logic then proceeds to a step 106, which provides that theoperator can continue with the inspection, i.e., proceed with decisionstep 92 in FIG. 5.

However, if the determination in decision step 102 indicates that theinspected component is not okay, a decision step 108 enables theoperator to determine if immediate attention is required. If so, theoperator presses red control button 56 at a step 110 and enters thecondition of the component on the handheld unit. For example, if theoperator is inspecting a tire and determines that the tread of the tireis separating, i.e., that the tire should not be used but should insteadbe replaced, the operator would use the cursor control on the portabledevice to select an option for the condition “tread separating fromtire” at a step 112. In many types of inspections, the operator will berequired to contact a supervisor for instructions regarding the safetycondition, at a step 114. In the example just noted, the supervisorwould likely arrange for the tire to be replaced by maintenance orrepair personnel before the operator makes a trip in the vehicle.

In some cases, a supervisor might override the operator's determinationof the state of the component based upon the reported condition.Therefore, a decision step 116 determines if the supervisor has givenauthorization to the operator to make the trip, scheduling a laterrepair of the component. If so, the logic proceeds to step 106, in whichthe operator continues with the inspection as described above. If not,there is no further need to inspect the remainder of the vehicle at thatpoint, since the complete inspection will need to be carried out againafter the unsafe condition has been corrected, e.g., by replacing thedefective tire. The logic is then done, as indicated in step 118.

In the event that the operator determines that immediate attention isnot required at decision step 108, at a step 120, the operator pressesyellow control button 54 on portable device 20. The operator thenselects and enters the condition noted on the portable device, asindicated in a step 122. In the example shown in FIG. 4, five possibleconditions are indicated by statements on display screen 40 for a tirethat is still usable but needs service. In this case, the operatoremploys cursor control 50 to move the cursor to a selected statementthat thus describes the observed condition of the component and thendepresses red control button 56 to enter the condition, creating arecord of the state and condition of the component currently beinginspected that is retained within the memory of the portable device.Thereafter, the logic proceeds to step 106, in which the operatorcontinues with the inspection.

Alternative Embodiments of Portable Device

Two additional embodiments of the portable device are illustrated inFIGS. 8 and 9, and 10 and 11, respectively. A portable device 140, whichis shown in FIGS. 8 and 9, has a top housing 142, which is joined to abottom housing 144 and includes a display bezel opening 148. Only aportion of a top surface 146 of the top housing is illustrated in theseFigures, although further details of the top surface are generallysimilar to the embodiment shown in FIG. 11, which is discussed below.

As clearly illustrated in the exploded view of FIG. 8, a substantiallytransparent protective plastic window 150 is mounted behind displaybezel opening 148 to protect the upper surface of a liquid crystaldisplay (LCD) 152. LCD 152 underlies the protective plastic window andis mounted on a printed circuit (PC) board 154, along with a number ofother components (including CPU 62, memory 64, component sensor 46, andcontrol 68, as shown and described above in connection with FIG. 3). Aplurality of corner supports 156 engage side tabs 158 on PC board 154.In addition, a plurality of threaded fasteners 160 (only one of which isshown) extend between top housing 142 and bottom housing 144, to securethe two housings together, locking PC board in a position defined bycorner supports 156 in cooperation with side tabs 158.

A front bezel 162 is seated at a front end of top housing 142 and bottomhousing 144 and includes a lens 164 that is substantially transparentand serves to focus light emitted by a plurality of light emittingdiodes (LEDs) 166, which emit white light. LEDs 166 are electricallycoupled to PC board 154 by leads 168, which are soldered to appropriateelectrically conductive trace connections (not shown) on the PC board154. An elastomeric seal 170 is fitted around front bezel 162 to sealout dirt, moisture, and other contaminants from the interior of portabledevice 140. Since LEDs 166 are disposed immediately behind lens 164, thewhite light emitted by the LEDs is generally focused by lens 164 so thatit can be directed by the operator of the portable device onto acomponent that is being inspected. Such components are sometimesdisposed in areas that are not well illuminated by ambient light. Thus,the light from LEDs 166 better enables an operator to use portabledevice 140 to more clearly see a component that is being inspected andto better observe the condition of the component in order to determineits safety status. Including LEDs 166 on the portable device avoids theneed to use a separate flashlight or other source of light to inspectcomponents that are not well lighted by ambient light, or which must beinspected at night.

A portable device 140′ is illustrated in FIGS. 10 and 11, and likeportable device 140, also includes a light source that can beselectively energized by an operator to illuminate a component that isbeing inspected, or for other purposes. However, portable device 140′also includes a digital camera 200 that can be selectively activated bya user to record an image, e.g., an image of a component that is beinginspected. Accordingly, if an operator makes a decision regarding thesafety status of a component or makes a decision to replace a component,a digital image captured by digital camera 200 can provide evidence thatjustifies the decision made by the operator. Portable device 140′ issubstantially identical to portable device 140 in most respects, exceptthat it has a lower housing 144′ in which digital camera 200 isincluded. Digital camera 200 has a bezel 202 that supports a lens 204for receiving light from a component that is being imaged by the digitalcamera. Not shown is a light sensitive element disposed inside thehousing and mounted to an underside of the PC board. The light sensitiveelement, which may comprise an array of charge coupled devices (CCDs) ora complimentary metal-oxide semiconductor (CMOS), produces digital datacorresponding to the light intensity at each pixel within a digitalimage that is being recorded. Although a higher quality might beachieved with a CCD light sensor, lower cost CMOS light sensors haverecently become available that can also be used for the light sensitivedevice of the digital camera. Such devices are available from a numberof different sources and can readily be integrated into portable device140′.

For purposes of aiming and framing a desired image to be captured bydigital camera 200, display 152 is switched to an imaging mode todisplay an image of the component. When framed as desired, the imageshown on the display can be captured in real time, in association withthe digital data corresponding to component being imaged and the imagedata can be stored within memory 64 (FIG. 3) of portable device 140′. Itis not expected that an operator will need to record image data for eachcomponent being inspected, since only those components having acondition other than okay might need to be photographed with the digitalcamera, as evidence of the status of the component, should any questionregarding the operator's decision subsequently arise. The image dataproduced by digital camera 200 will likely be stored in a compressedformat, such as the Joint Photographic Experts Group (JPEG) format whichemploys a lossy compression scheme, as is commonly done with otherdigital cameras. The image data will thus be retained with the otherdata input by the user during an inspection and will be downloaded tolong-term storage with the other data from the inspection.

FIG. 11 illustrates further details of top surface 146 of portabledevice 140′ (and 140). Controls included on the front surface include aRight cursor control button 210, a Left cursor control button 212, an Upcursor control button 214 and a Down cursor control button 216. Centeredbetween these four control buttons is a Read/Enter control button 218,which is depressed when a user wants to enter a selection currentlyhighlighted (selected) on display 152. Since both portable device 140and portable device 140′ include the internal white LED light source, alight power switch 220 is included that can be momentarily depressed bya user to energize the LEDs, to illuminate a component that is beinginspected, or to produce light for some other purpose of the operator.Adjacent to Up cursor control button 214 and opposite from light powerswitch 220 is an Info/Menu button 222 that can be depressed at any timeto bring up a current menu on display 152. During the inspection, whileviewing the condition of each component being inspected, the user willhave an option and will be prompted to press either a green controlbutton 224, which is also pressed to indicate a Yes condition, or a redcontrol button 226, which is also pressed to indicate a No condition.

Neither the second or third embodiments of the portable device include ayellow button. Instead, if the condition of the component is not okay,the operator is simply prompted to select one of several predefinedconditions that represent the status of the component being inspected,which can range from a condition in which the component may still beusable, to a condition that justifies immediate repair/replacement ofthe component. These conditions are presented to the operator on display152. Using the cursor control buttons, the operator selects theappropriate entry of the condition on the display and depressesRead/Enter control button 218. Furthermore, if the condition of acomponent is not okay, the operator will be prompted to record a digitalimage of the component. If the operator presses green button 224 inresponse to this prompt, display 152 will then switch to the imagedisplay mode to show the image that might be captured by digital camera200. Once the operator has directed lens 204 of the digital camera andpositioned the portable device so as to frame the component as desired,as indicated by the image on display 152, the operator depressesRead/Enter control button 218 to capture the image of the component,storing the corresponding image data produced by the digital camerawithin the memory of the portable device.

A power On/Off switch 228 is disposed between green control button 224and red control button 226 and slightly offset therefrom. Below thepower On/Off switch is a charge indicator 230, for indicating the chargecondition of the internal battery supply (not shown) that is containedwithin the housing of the portable device. A power/data connector port232 is disposed on an end of the portable device for connecting to anexternal cradle or docking station, which is discussed in greater detailbelow. Neither portable device 140 nor portable device 140′ include anexternal stub antenna, as in the first embodiment. Instead, an antenna(not shown) is included internally within the upper and lower housingsof the portable device. Use of an internal antenna is preferred, sinceit avoids potential breakage of an external antenna. It has beendetermined that an external antenna is not required for sensing RFIDtokens. However, like the first embodiment of the portable devicedescribed above, portable devices 140 and 140′ are used to sense whenthe portable device is within sufficient range of a token to ensure thatthe operator is then positioned to inspect a component, to determine thesafety status of the component, or to evaluate some other parameter ofthe component. The other types of tokens and sensors discussed above inconnection with the first embodiment of the portable device are alsocontemplated for use with either the second or third embodiments of theportable device. Accordingly, those options need not be furtherdiscussed in regard to portable devices 140 or 140′.

FIG. 12 illustrates the steps involved in using either portable device140 or 140′ in connection with carrying out an inspection on a vehicleor other type of apparatus or processing facility. Carrying the portabledevice, an operator starts the inspection, and as indicated in a step300 uses the portable device to read an operator ID, to input dataidentifying the operator who is currently using the portable device.This ID can be read from a token associated with the operator, forexample, a token that is carried by the operator on a keychain or as apart of a photo identification card. The operator ID is then recorded aspart of the data associated with the current inspection and stored inthe memory of the portable device for later transmittal and storage at aremote site.

A step 302 then provides that the operator reads an asset ID for thevehicle or apparatus or processing equipment being inspected, which isalso stored within the data associated with the current inspection andis provided by a token, which is attached to the asset. Alternatively,the operator might manually enter an asset ID before undertaking theinspection. Having input the asset ID, the operator proceeds to thefirst inspection point.

In a step 304, the presence of the portable device (and of the operator)is verified at a token fixed adjacent to the first inspection point. Theportable device automatically senses the token and stores data providingproof that the operator had physically carried the portable device tothe inspection point associated with the token. Next, a step 306indicates that a prompt to the operator is displayed on the portabledevice, indicating the next steps of the inspection to the operator. Asnoted above, a series of inspection steps may be required to complete aninspection of a specific component, or the operator may be prompted toinspect several components that are all associated with the currenttoken. Following step 306, in a decision step 308, the operatordetermines if the inspected part is okay. If so, the operator pressesthe green control button on the portable device as indicated in a step310. A decision step 312 then determines if there are any remainingzones or points to be inspected during the current inspection and if so,a step 314 provides that the operator moves to the next zone or pointwhere one or more components are disposed that require inspection. Thelogic then returns to step 304. Alternatively, if there are no remainingzones, the operator has concluded the inspection.

Returning to decision step 308, in the event that the inspected part orcomponent is not okay, the operator would press the red control buttonat a step 316 and as prompted on the display, would enter or select acondition of the component that led the operator to conclude that itscondition was not okay. Display 152 on the portable device would thenprompt the operator to decide whether to take a picture, at a decisionstep 318, of the component (this option only applies to portable device140′). If the operator decides to take a picture of the component, astep 320 enables digital camera 200 to be used to create image data forthe item. As described above, display 152 shows the image that is to berecorded in real time, enabling the operator to frame the picture bypositioning the portable device relative to the component so that thedesired image of the component appears on the display. The operator thenpresses the Read/Enable control button, capturing the image as it thusappears on display 152, so that the image data are recorded within thememory of the portable device. Thereafter, the logic continues withdecision step 312. If the user is employing portable device 140 ratherthan portable device 140′, following step 316, the logic would proceeddirectly to decision step 312, since there would be no option for takinga picture.

Docking Station

FIGS. 14 and 15 illustrate a docking station 400 for the portable deviceof the present invention. Docking station 400 includes a housing 402having a receptacle 404 into which either portable device 140 or 140′can be fitted. FIG. 15 illustrates portable device 140′ inserted withinreceptacle 404 to facilitate downloading of the data stored within theportable device to a remote storage. The docking station 400 includes anindicator light 406 that changes color to indicate that data are beingtransmitted from portable device 140 or 140′ to another device. Dockingstation 400 includes an interface circuit that couples the data port onportable device 140 or 140′ to a personal computer 422 through a lead420, as shown in FIG. 16. The interface circuit converts the data formatof portable device 140 and 140′ to a universal serial bus (USB) orserial RS-232 format for communication with personal computer 422.Accordingly, data link 420 is connected either to the USB port or serialport on personal computer 422 from a port 408 on docking station 400(see FIGS. 14 and 15). It is also contemplated that other types ofcomputing devices might be used instead of portable computer 422, andother types of data format can be employed. As shown, portable computer422 has a display monitor 424 and a hard drive 426 for recording datatemporarily transferred from portable device 140 and 140′. Subsequently,the data stored on hard drive 426 are downloaded through a data link428, over Internet 430, and through a data link 432 to a remote server434, which includes additional storage in the form of a plurality ofhard drives 436. It is contemplated that docking station 400 might bedisposed in a terminal or other location to which the portable device isreturned between inspections or at other times, to transfer data fromthe memory within the portable device to remote storage on remote server434.

Data links 428 and 432 can each comprise a telephone modem connectionover a telephone network, a wireless data link, a broadband connectionthrough a DSL interface or cable modem, or a cell phone link.Alternatively, personal computer 422 can be directly connected over alocal area or wide area network to remote server 434. In general, it isonly necessary that the data stored within portable device 140 or 140′resulting from one or more inspections be transferred to a morepermanent storage, whether in personal computer 422 or in remote server434, so that the memory within the portable device is thereafteravailable to store data from further inspections. By providing remotestorage of the data that is downloaded from the portable device fromtime to time, the security and maintenance of the data are ensured.

FIG. 13 illustrates another aspect of the present invention. Forpurposes of carrying out safety inspections of a bus 360, which may be aschool bus, a last safety check made by the operator (e.g., the driver)might be a check to ensure that all of the passengers have exited fromthe bus. As shown in FIG. 13, bus 360 includes a plurality of seats 362at spaced-apart intervals along an aisle 364. To ensure that a child hasnot fallen asleep or hidden below or behind the seats, at the end of theroute, the driver should make a thorough visual inspection of all of theseats in bus 360, which can only be done by walking to the rear of thebus. Accordingly, a token 366 is attached to the back of a seat 368disposed adjacent to the rear of the bus. By bringing the portabledevice in proximity with token 366, the operator can thereby confirmthat the rear of the bus was visited at the end of a route to ensurethat the driver at least had the opportunity to visually confirm that nopassengers remained on the bus. Without making such an inspection, it ispossible that child might remain on a bus when it is returned to afacility for storage, which at the very least, would cause considerableconcern to the parents of the child. Thus, the present invention helpsto ensure that the driver is motivated to make an inspection to ensurethat no child remains on the bus at the end of a route.

Other Type of Portable Device

While it is likely that an initial preferred embodiment will employportable device 20, 140, or 140′, it is also contemplated that anaccessory might be provided for a personal digital assistant (PDA), suchas the PALM™ PDA, that would enable the PDA to be used for the samefunctions as the portable devices discussed above. The accessory to thePDA would include a sensor to detect when the PDA is within thepredetermined maximum range from the token associated with the componentcurrently being inspected. The conventional controls on the PDA can beused to make and enter a selection. Furthermore, instead of using acursor control, it is also contemplated that a touch screen displaymight instead be used for making selections of menu items and otheroptions presented to the operator. In addition, the PDA would need to beprogrammed to carry out the functions implemented by the portabledevices described above.

Other Applications of the Present Invention

Although the present invention will initially be used in connection withsafety inspections of tractors and trailers in the commercial truckingindustry, there are many other types of safety inspections unrelated tovehicles in which it is equally applicable. Other types of vehiclesbesides trucks, such as aircraft and buses, can also benefit from use ofthe present invention to provide proof that the components of thevehicle have been visited and observed by the operator or other persondoing an inspection. Still other applications of the invention are notrelated to vehicles. For example, in a chemical processing plant or apetroleum refinery it is common for technicians to make periodic safetyinspections of valves, gauges, reactors, pressure vessels, and othertypes of processing equipment and system components to ensure that theyare operating properly and within nominal or acceptable limits. Duringan inspection, a technician may note that a valve is leaking slightly,and schedule it for repair or replacement at a later date. Clearly, ifthe leak is of a non-hazardous substance and is insignificant in volume,there might well be no reason to shut down the process line in which thevalve is installed simply because of the leaking valve. However, if thevalve controls an extremely hazardous or toxic substance, even a smallleak may be unacceptable. In this case, the technician shouldimmediately report the leaking condition of a valve to a supervisor whowould then likely shut down the process or divert the flow of hazardoussubstance to a different process line to enable the condition to becorrected by immediate replacement or repair of the valve. Additionalapplications, without any implied limitation, include the inspection ofamusement park rides, such as roller coasters, etc., where the conditionof many different components of the ride can directly impact on itssafety.

While the preceding discussion discloses how a first preferredembodiment of the present invention is used in recording data related tosafety inspections of a vehicle, it should be evident that portabledevice 20, 140 or 140′ is readily adapted to recording data fromvirtually any type of inspection. In the example of a non-vehicularinspection in a chemical processing plant just noted, a technician wouldbe prompted by the portable device to inspect the valve, and once theportable device was within a predetermined distance of the valve, wouldbe prompted to indicate a state of the valve. If the techniciandepressed either yellow control button 54 or red control button 56 (onportable device 20), or red button 226 (on portable device 140 or 140′),the display would provide a menu of possible conditions from which thetechnician could select, using the cursor control to select and indicatethe observed condition of the valve. Also, other conditions that are notdirectly related to safety can be recorded with the present invention.

Contemporaneous and Automatic Collection of Ancillary Data During anInspection

Another embodiment disclosed herein relates to the collection ofancillary data during an inspection. The term ancillary data is intendedto refer to data that does more than simply verify that an inspector waspresent at a particular location, checkpoint, or component during aninspection. For example, in the embodiments described above, wherein aplurality of tokens are affixed to predefined inspection locations,preferably each token will provide a unique ID to the portable device,such that the records stored by the portable device can be used todetermine each location that was visited during an inspection. If datacorresponding to particular token or location is missing from the recordgenerated by the handheld device during the inspection, such anoccurrence can indicate that the particular token or location was notvisited by the inspector during the inspection (of course such anomission could also indicate that there was a communication failurebetween that token and the portable device). Such ID data is notancillary data, because the only function of the ID data is to verifythat an inspector was present at a particular location or component. Incontrast, ancillary data is intended to represent data that has anadditional utility. For example, a sensor may be disposed in proximityof the component or location to be inspected. Data collected by such asensor represents ancillary data, because such data does more thanuniquely identify a particular location or component that was to bevisited during an inspection. In accord with one exemplary embodiment,during an inspection, ancillary data will be collected from at least onelocation or component during an inspection. It should also be recognizedthat the ancillary data can be collected by a sensor disposed at alocation other than the location of a token configured to convey theancillary data to a portable device. While most often the ancillary datawill likely be generated proximate the location where the ancillary datais conveyed to the portable device, it should be recognized that such arequirement is not a limitation of the concept described herein. Thus,ancillary data can be collected from a first location, but conveyed to aportable device from a different location, as long as a logicalconnection is provided between the sensor and the token or other unitconfigured to convey the ancillary data to the portable device.

Thus, another embodiment described herein relates to extracting datastored in a token using a portable reader generally consistent withthose described above (i.e. portable device 20, 140 or 140′). It shouldbe understood that while in one embodiment the extraction of ancillarydata using a portable reader encompasses using a portable reader toextract data from a modified token (a token including a memory orcoupled with a memory), the overall concept of collecting ancillary dataduring an inspection presented herein also encompasses conveyingancillary data from a sensor to a portable reader, regardless of whetherthe sensor is considered a token. While in a particularly preferredimplementation the portable reader will extract the data from thesensor/token without requiring a physical connection between thesensor/token in the portable reader, the concept disclosed herein alsoencompasses embodiments in which a physical connection must be madebetween the portable reader and the sensor/token in order to extractdata from the sensor/token. The IBUTTON™ computer chip, discussed above,represents an exemplary data interface that requires a physicalconnection with a portable reader to extract data. Of course,conventional data ports including serial ports, parallel ports, and USBports can be used to implement a data interface requiring a physicalconnection with a portable reader, such that a portable reader canextract data from a sensor/token. It should thus be understood that thedisclosure presented herein further encompasses a modified token orsensor configured to 1) collect ancillary data; 2) store ancillary data;and 3) enable the stored ancillary data to be automatically conveyed toa portable reader. FIGS. 17-20 relate to the collection and conveyanceof ancillary data in accord with another aspect of the concept disclosedherein.

FIG. 17A is a block diagram schematically illustrating three differenttypes of data that can be collected by the portable devices describedherein during an inspection, in which ancillary data are collectedcontemporaneously with the inspection. It should be understood thatconsistent with the above discussion, token 504 can be implemented usinga number of different components enabling data to be exchanged betweenthe token and the portable device. While an RFID tag represents one typeof token that is particularly useful for this purpose, it should beunderstood that the concepts disclosed herein are not limited toembodiments where tokens are implemented as RFID tags.

Token 504 can be configured to provide a token ID alone, as indicated ina block 506. As discussed above, token IDs enable individual tokens tobe uniquely discriminable, such that a record stored in the portabledevice of a specific token ID will indicate that the user of theportable device was proximate that specific token during an inspection.As discussed in greater detail below, token 504 can be configured tocommunicate both ancillary data (such as sensor data) and a token ID toa portable device, has indicated in a block 508. Alternatively, token504 can be configured to communicate only the ancillary data to aportable device, as indicated in a block 510.

FIG. 17B is a block diagram schematically illustrating a sensor 502 alogically coupled to a token 504 a, such that when a portable deviceconsistent with those described herein is proximate token 504 a, theportable device will automatically collect both token ID data andancillary data that have been collected by sensor 502 a. It should beunderstood more than one sensor can be logically coupled to a singletoken, as indicated by optional sensor 502 b.

FIG. 17C is a block diagram schematically illustrating a sensor 502 cacting as a token, such that when a portable device consistent withthose described herein is proximate sensor/token 502 c, the portabledevice will automatically collect ancillary data collected bysensor/token 502 c, but without also collecting any unique token ID.Such a configuration can be implemented when the data collected by thesensor uniquely identifies a location associated with the inspection sothat an ID is not required. For example, if one inspection locationspecified for a vehicle inspection corresponds to an engine compartmentof the vehicle, and sensor/token 502 c is configured to collect enginedata (e.g., one or more parameters such as oil level, oil temperature,coolant temperature, etc.), and no other engine data are collected inany other part of the inspection, the presence of such engine data inthe record generated by the portable device during the inspection willprovide evidence that the inspector was proximate sensor/token 502 cduring an inspection of the vehicle. Thus, if ancillary data collectedduring an inspection can uniquely identify a particular location, then atoken ID need not be collected by the portable device while the operatoris inspecting that location. With respect to implementing sensor/token502 c, it should be understood that sensor/token 502 c encompasses anytype of sensor configured to communicate with a portable device, as wellas a sensor logically coupled to a token configured to communicate withthe portable device, where the token is not configured to provide aunique token ID to the portable device. All possible combinations of thesensor/token embodiments illustrated in FIGS. 17A-17C are alsocontemplated as being useful during inspections with the portabledevices, where the token/sensor at one or more locations included in aninspection can correspond to the token/sensor embodiment in any of thesethree Figures.

Accordingly, FIG. 18 schematically illustrates a public transportationvehicle including a plurality of tokens, some of which are configured toconvey to a portable device only a token ID, some configured to conveyto a portable device only ancillary data, and some configured to conveyto a portable device both a token ID and ancillary data. It should beunderstood that the concepts disclosed herein are not limited toapplication with any specific type of public transportation vehicle, andcan be equally applied to vehicles such as trains, marine vessels, andaircraft. Furthermore, the broad concept of collecting ancillary datacontemporaneously with an inspection, while using a portable device thatprovides a record of locations that were visited during an inspection,can be implemented for any type of inspection, and is not limited to aninspection of a vehicle. Thus, the exemplary embodiment disclosed withrespect to FIG. 18 should not be considered to limit the applicabilityof the concepts disclosed herein.

Public transportation vehicle 512 is a bus, which includes a pluralityof tokens 514, which are positioned in overhead luggage compartments516. The purpose of tokens 514 is to ensure that an inspector waspositioned proximate to each overhead luggage compartment during aninspection. When one of the portable devices disclosed herein ispositioned proximate to any of tokens 514, the portable device willcollect a unique token ID from each token 514, providing a record thatthe inspector was proximate to each of the overhead luggage compartmentswhere the token is disposed. While not providing proof that theinspector actually inspected each luggage compartment, such a recorddoes provide proof that the inspector was proximate to the overheadluggage compartments and could readily have inspected the overheadluggage compartment. Clearly, it is intended that, while proximate toeach of the overhead luggage compartments, the inspector will search forany contraband, toxic material, explosive material, or any otherundesirable or other materials that may have been left behind by thelast group of passengers to use vehicle 512. This inspection willprovide assurance to the next group of passengers that the vehicle issafe for their use. Note that tokens 514 are configured to communicateonly a token ID to the portable device. It should be understood,however, that other types of inspections, and not simply inspectionsdesigned to minimize terrorist threats, are encompassed by the conceptsdisclosed herein and defined by the claims that follow.

Vehicle 512 also includes a plurality of tokens 520, each of which aregenerally positioned underneath a different group of seats 518. Thepurpose of tokens 520 is to ensure that an inspector was positionedproximate to each group of passenger seats during an inspection. Whenone of the portable devices disclosed herein is positioned proximate toany of tokens 520, the portable device will collect a unique token IDfrom that token, providing a record that the inspector was proximate tothe corresponding group of passenger seats in the vehicle. Again, whilenot providing proof that the inspector actually inspected a group ofseats, such a record does provide proof that the inspector was proximateto the seats in the group. It is the intention that, while proximate toeach group of passenger seats, the inspector again will search for anycontraband, toxic material, explosive material or any other undesirableor other materials that may have been left behind by the last group ofpassengers to use vehicle 512. This actual inspection will provideassurance to the next group of passengers that the vehicle is safe fortheir use. Note that tokens 520 are configured to communicate only atoken ID to a portable device.

Vehicle 512 were further includes a plurality of tokens 522, each ofwhich are positioned proximate to the vehicle tires 523. Significantly,each token 522 is logically coupled to a sensor 524. Those of ordinaryskill in the art will recognize that sensors 524 can be configured tocollect a wide variety of data related to vehicle tires, which vehiclemaintenance personnel may have an interest in having collectedcontemporaneously with an inspection of the vehicle. For example,sensors 524 can be configured to collect tire pressure data, datarelated to the wear of brake components associated with the tire, tiretemperature data, or various combinations of different types of datavalues. Each token 522 is configured to communicate to a portable device(consistent with those described above) both a token ID, as well asancillary data collected by sensors 524. The token ID can be used tocorrelate specific ancillary data to a specific tire. Thus, if therecord automatically collected by the portable device indicates that aspecific one of the vehicle's tires is seriously under inflated, thetoken ID associated with the ancillary data can be used to identifywhich tire needs attention. Those of ordinary skill in the art willrecognize that once such data have been collected, a plurality ofdifferent techniques can be used to manage the data. For example, theportable device can be configured to provide a warning to the inspectorthat the ancillary data identify an unsafe condition that needs to beaddressed before the vehicle can be placed into service. Furthermore, ifthe portable device is equipped to connect to a data management service(such as vehicle fleet management database, as are used by manyoperators of fleets of vehicles) via a remote transmission, once such anunsafe condition has been indicated in the ancillary data, the portabledevice can communicate the unsafe condition to the data managementservice. Operators at the data management service can then implement oneor more appropriate responses, such as dispatching a repair crew to dealwith the unsafe condition, or documenting that the vehicle is unfit forservice and dispatching a replacement vehicle.

It should be recognized that many types of sensors collecting manydifferent kinds of ancillary data are encompassed by the conceptprovided herein. Other sensor/token combinations can include (withoutlimitation) combinations configured to detect and convey vehicle mileagedata, vehicle engine parameters (including engine hours), fluid levelsand consumption rates, equipment parameters, environmental conditions,positional/location information, etc. The specific sensors noted aboveare intended to be exemplary, rather than limiting, since almost anytype of sensor can be used.

Vehicle 512 also includes at least one token 526, which is configured tocommunicate only ancillary data to a portable device (consistent withthe description above with respect to FIG. 17C). As noted above, ifancillary data communicated by token 526 uniquely identify the locationassociated with an inspection, then no token ID need be communicated toa portable device for the location. As indicated in FIG. 18, token 526is disposed in the front of vehicle 512, generally proximate to thevehicle operator's seat (i.e., generally near the steering wheel andother vehicle controls). Those of ordinary skill in the art willrecognize that many vehicles are equipped with onboard computers tomeasure and manage regular vehicle operating conditions, such as engineparameters, and in some vehicles, other vehicle subsystems as well,including brake systems, engine power transmission systems, fuelsystems, and suspension systems. Thus, token 526 can be configured tocommunicate a variety of ancillary data collected by the onboardcomputer to a portable device, while the inspector is inspecting aparticular portion of the vehicle, such as a driver's seat location.Some vehicles are equipped with positioning systems, such as globalpositioning satellite (GPS) based systems for determining the locationof the vehicle. The ancillary data provided by token 526 can alsoinclude such positioning data. Note that while token 526 does notcommunicate a token ID to a portable device responding to the proximityof token 526, the ancillary data from token 526 can be easilydifferentiated from any other ancillary data collected during theinspection, thereby providing evidence that an inspector was proximatetoken 526 during an inspection. It should be understood that tokenscommunicating only ancillary data to a portable reader/device configuredto communicate with the token are not limited to being implemented inany specific location, as long as ancillary data communicated to aportable reader by such a token can be used to uniquely identify thatlocation in an inspection. Thus, the description of token 526 containedherein is intended to be exemplary, rather than limiting. Also, in sometypes of inspections, the data may not necessarily be of a nature thatuniquely indicates the inspection was made of a specific location, butwill at least indicate the data have been collected by the inspector.

In particular, with respect to the pre-trip inspection reports discussedin detail above, operators of commercial vehicles require data abouttheir vehicles to properly manage their fleets. If such ancillary datacan be automatically collected contemporaneously with a required vehicleinspection, operators of such vehicles will be able to collect valuabledata with no additional effort. The only effort required is to equiptheir vehicles with sensors configured to collect the ancillary data,and tokens configured to communicate that ancillary data to the portablereader. Once a vehicle has been thus modified, ancillary vehicle datacan be automatically collected during each inspection. With respect topre-trip vehicle inspections, ancillary data that fleet operators arelikely to desire include one or more of the following: tire pressuredata for each vehicle tire, tire temperature data (e.g., maximumtemperature for each vehicle tire), brake condition data (such as brakestroke data), engine hour data, fuel level data, fuel consumption data,oil temperature data, oil level data, coolant temperature data, coolantlevel data, engine temperature data, and vehicle location data (i.e.,GPS data).

It must be emphasized that the term “ancillary data” is intended toencompass a wide variety of different types of data. Indeed, the type ofancillary data communicated to a portable device during an inspectionwill largely be a function of the type of inspection that is beingconducted. If the inspection is related to a vehicle, the ancillary datawill likely involve data relating to the condition of the vehicle or oneof the components or subsystems comprising the vehicle. If theinspection is related to a building, the ancillary data will likelyinvolve data relating to a condition of the building, or one of thebuilding's subsystems (such as an alarm system, a computer system, aheating system, a cooling system, etc.). Generally, ancillary dataencompass any data other than static data that uniquely identify aspecific token.

While RFID tags represent a particularly useful token implementation, itshould be recognized that currently available RFID tags generally have arelatively low baud rate for transfer of data. To accommodate thisrelatively low data transfer rate, RFID tags configured to communicateancillary data can be selected to provide a plurality of outputs basedon a single request for data. For example, a standard RFID tag can holdten 4-bit nibbles of data. In order to send more data across the RFIDlink, a protocol can be provided that enables multiple transmissions ofRFID data over the RFID data link (preferably, a 125 kHz link). Anexemplary protocol will separate the data to be transmitted into aplurality of subsets. During an initial read, the RFID data linkidentifies the number of additional reads that will be transmitted,based on a single request for data. Subsequent reads will transmitsubsets of the data collected. For example, if the data to betransmitted include token identification data, tire pressure data, andtire temperature data, each of those different types of data can beconsidered a subset, to be transmitted as a separate read. If more thanone subset of data can be transmitted in a single read, then fewer readsthan the number of subsets can be employed.

While a data interface is readily implemented enabling data to becommunicated between a token or sensor and one of the portable devicesdescribed herein using an RFID tag, it should be understood that thepresent disclosure is not thus limited. The IBUTTON™ computer chipdiscussed above could also be used to implement the data interface(i.e., the IBUTTON™ computer chip might be used to simultaneouslyimplement the controller, the memory, and the data interface).Furthermore, it should be recognized that such a data interface can beimplemented with conventional data ports, including any of a parallelport, a serial port, a USB port, and a proprietary data port.

As noted above, with respect to using a portable device as describedherein to automatically collect ancillary data contemporaneously with aninspection, some mechanism must be provided for enabling data to beconveyed from a token or a sensor disposed proximate a location to beinspected, to the portable device. As schematically illustrated in FIG.19, an exemplary ancillary data conveying token 600 includes a datainterface 602, a controller 604, and a memory 606 (preferablynonvolatile). Preferably, a housing 622 encloses data interface 602,controller 604, and memory 606, although if the data conveying token isplaced in a protected location (such as within the cab of a vehicle),the housing is optional and not required. In one implementation, housing622 is waterproof and shock resistant, so that token 600 can be securedto the exterior of a vehicle or location to be inspected.

Controller 604 is central to the data conveying token. The controllercommunicates bi-directionally with data interface 602, and memory 606.In addition, the controller is also logically coupled to one or moresensors 614, which are configured to collect ancillary data to beconveyed to a portable reader by token 600 when the portable reader isin close proximity to the token, generally as described above. Asdiscussed above with respect to FIG. 18, examples of useful sensors areinclude a tire pressure sensor 616, a tire temperature sensor 618, and abrake condition sensor 620. It should be understood, however, that suchsensors are intended to be exemplary, rather than limiting theapplicability of the present disclosure. Preferably, the controller isimplemented as a microprocessor, such as a central processing unit (CPU)that executes a software program comprising machine instructions storedin the memory. Alternatively, the controller may be implemented using anapplication specific integrated circuit (ASIC). In either case, thecontroller is configured to execute a plurality of functions. Thosefunctions will typically include determining when the portablereader/portable device is sufficiently close to token 600 to convey theancillary data to the portable device (this function can be implementedby recognizing an interrogation signal received from portable device),and if the amount of ancillary data exceeds a data transfer rateachievable by token 600, formatting the ancillary data such that datatransmission can be achieved using a plurality of separate datatransmissions based on a single request for data from the portabledevice, generally as described above.

Where the controller includes a microprocessor, memory 606 can be usedto store machine instructions for enabling the microprocessor toimplement the plurality of functions described above, as well as forstoring the ancillary data.

Data interface 602 enables data to be extracted from the meteringdevice. In a preferred embodiment, the data interface is implemented asan RFID tag, enabling data to be extracted without requiring a physicalconnection between the data interface and the portable reader. Ancillarydata conveying tokens that implement data interface 602 using an RFIDtag can be read using any of portable devices 20, 140, or 140′. While aninitial prototype has implemented data interface 602 using an RFID tag,it should be understood that the concept is not thus limited. TheIBUTTON™ computer chip discussed above could also be used to implementthe data interface (i.e., the IBUTTON™ computer chip might be used tosimultaneously implement the controller, the memory, and the datainterface). Furthermore, it should be recognized that data interface 602can be implemented with conventional data ports, including any of aparallel port, a serial port, a USB port, and a proprietary data port.

With respect to the disclosure provided above relating to the use of thetoken and a portable reader, it should be understood that data interface602, controller 604, and memory 606, can be collectively considered as a“token.” Although not like the other types of tokens discussed above,these components interact with a reader that is used to extract datathrough the data interface and thus to that extent, function like theseother types of tokens.

In one implementation, the data interface discussed above is implementedusing a coil. Those of ordinary skill in the art will recognize thatRFID tags convey data using a coil. Commercially available devicesincluding a memory, a coil (and sometimes an integrated processor) arereferred to as transponder interfaces. Particularly preferredtransponder interfaces, such as types U3280M™ or U3280B™, are availablefrom Amtel Corp. of San Jose, Calif. Amtel also provides a transponderinterface that includes an integrated controller, the U9280M-H™, whichwould avoid the need for a separate microprocessor. It should beunderstood that similar products from other vendors can be employed, andthe present disclosure is not intended to be interpreted as beinglimited to a specific transponder interface integrated circuit.Furthermore, it should also be recognized that the data conveying tokendescribed above is intended to be exemplary, rather than limiting. Thoseof ordinary skill in the art will recognize that many differentpossibilities exist for conveying data to a portable device during aninspection. As noted above, data can be conveyed from a token or othercomponent to a portable device via wireless communication or by ahardware link between the component conveying the data and the portabledevice. The concept of collecting ancillary data during an inspection isnot limited to any specific technique for conveying data from acomponent disposed at a location associated with an inspection, and theportable device used to generate a record of the inspection. It shouldalso be recognized the term token as used herein is intended to beinterpreted broadly. Tokens represent any type of component that can bedetected by a sensor in the portable device. Some tokens are configuredto convey identifying data to the portable device, such as a token ID.Other tokens are configured to convey only ancillary data to a portabledevice. Still other tokens are configured to convey both ancillary dataand a token ID to a portable device. Exemplary tokens include RFID tagsand IBUTTON™ computer chip, although such examples are simply intendedto be exemplary, rather than limiting on the scope of this disclosure.

With respect to tokens configured to convey ancillary data and no tokenID, it should be recognized that an inspection could involve inspectinglocations in which every single token is configured to convey onlyancillary data and no token ID, in which case, the ancillary data itselfprovides not only the additional information comprising the valuesincluded in the data, but also provides data that can be used to verifythat an inspector was proximate each location or component included inthe inspection. This conclusion would require that the ancillary dataconveyed by each token be sufficiently unique to enable that data to bedistinguishable from data conveyed by other tokens disposed at otherlocations or components involved in the inspection. For example,consider an inspection of a restaurant, in which the restaurant ownerwants an inspection to be performed nightly to determine that the stovehave been turned off (to avoid an accidental fire), that therefrigeration unit is working properly (to avoid spoilage of foodproducts), and that the safe has been secured (to prevent employees orothers from being tempted to commit a theft). The closing manager istasked with using a handheld device such as those described above toperform this inspection every night before leaving. A token proximate tothe stove can be configured to convey ancillary data to the handhelddevice indicating whether the stove is on or off. The token proximate tothe refrigeration unit can be configured to convey ancillary data to thehandheld device indicating the ambient temperature in the refrigerator.The token proximate to the safe can be configured to convey ancillarydata to the handheld device indicating whether the safe is locked. Atthe end of the inspection, if the inspection has been properly executed,the record generated by the handheld device will include: a valueindicating whether the stove gas valve has been turned off or left on(corresponding to the state of the stove), a temperature value(corresponding to the temperature inside the refrigerator), and a valueindicating whether the safe is locked or open (corresponding to thestate of the safe). If the record contains no temperature value, it canbe inferred that the manager failed to inspect the refrigerator. If therecord contains no value for the stove gas valve, it can be concludedthat the manager failed to inspect the stove. Similarly, if the recordcontains no value indicating the locked state of the safe, it can beconcluded that the manager failed to inspect the safe.

Method of Automatically Collecting Ancillary Data During an Inspection

FIG. 20 is a flow chart 530 schematically illustrating a sequence oflogical steps employed in using a portable device consistent with thosedescribed herein to collect ancillary data during an inspection. From astart block 532, a first step optional step is to enter an operatoridentification number (ID) into the portable device, as indicated in ablock 534. As discussed in detail above, it would be desirable to beable to identify a particular individual conducting an inspection, so ifthe record generated by the portable device during the inspectionindicates that a particular location was missed during an inspection,feedback can be given to the correct individual, to ensure that futureinspections are conducted more thoroughly.

Once the operator ID is entered (if required), the portable deviceprompts the operator to proceed to a first inspection point as indicatedby a block 536. A decision block 538 determines if the portable devicehas detected the token associated with the component or location that isto be inspected, by determining if a token ID has been detected. If not,then the logic determines if the portable device has detected anyancillary data being conveyed to the portable device, as indicated in adecision block 544. If not, the logic loops until either a token ID orancillary data is detected, indicating that the portable device isdisposed proximate to the token or sensor configured to provide at leastone of a token ID and ancillary data to the portable device.

Referring to decision block 538, once the portable device has detected atoken ID, the token ID is stored in the memory in the portable device,as indicated a block 540. In a decision block 542, the logic determinesif any ancillary data are also being detected, along with the token ID(as discussed in detail above, some tokens are configured to convey bothtoken ID and ancillary data to a portable reader, while other tokens areconfigured to convey only ancillary data, or only a token ID). Ifancillary data are detected, the ancillary data are stored in thememory, as indicated in a block 546.

Referring to decision block 544, once the portable device has detectedancillary data, the ancillary data are stored in the memory in theportable device as indicated in block 546. Regardless of which path istraversed to reach block 546, the portable device then prompts theoperator to perform the inspection of the location or componentproximate to the token, as indicated by a block 548. As discussed indetail above, the portable device may give specific prompts to theoperator indicating the conditions or components that are to beinspected. In the context of inspecting public transportation vehiclesto minimize terrorist threats, the portable device will likely promptthe operator to look for unattended packages, bags, or containers, whichmay contain explosive devices, or toxic materials.

In a decision block 550, the controlling logic determines if there arefurther inspection points or locations in the inspection currently beingcarried out. If not, the data collected by the portable device (theancillary data and the record of the token ID's recognized during theinspection) are transmitted or uploaded into storage at a remote site,as indicated in a block 554. As discussed in detail above, this step canbe executed immediately after the inspection is completed, or at somelater time, perhaps after additional inspections have been completed,and/or after the portable device has been inserted into the externalcradle or docking station. Once the data are transmitted to the remotesite for long-term storage, the process is complete.

Assuming that further inspection points remain in the inspection atdecision block 550, a block 552 indicates that the operator is toproceed to the next inspection point, which will again preferably bedetermined by a prompt displayed to the operator on a display of theportable device. The logic then loops back to decision block 538, whichdetermines if the sensor on the portable device has detected a token ID,indicating that the portable device is within the predefined maximumrange of the token, thus ensuring that the operator is sufficientlyclose to the component to inspect it.

Although the present invention has been described in connection with thepreferred form of practicing it and modifications thereto, those ofordinary skill in the art will understand that many other modificationscan be made to the present invention within the scope of the claims thatfollow. Accordingly, it is not intended that the scope of the inventionin any way be limited by the above description, but instead bedetermined entirely by reference to the claims that follow.

1. A method for providing a record on a portable device that a locationwas visited during an inspection, while contemporaneously collectingancillary data on the portable device, comprising the steps of: (a)enabling an operator to move the portable device proximate the location;(b) in response to the portable device being moved proximate thelocation, automatically producing a record stored within the portabledevice that the portable device was proximate the location, said recordproviding evidence that the operator was sufficiently close to thelocation to perform an inspection at the location; and (c) further inresponse to the portable device being moved proximate the location,automatically transferring and storing the ancillary data in therecording device, said ancillary data having been collected by a datacollection device disposed proximate the location.
 2. The method ofclaim 1, further comprising the step of affixing a token adjacent to thelocation, said portable device responding to the token to detect whenthe portable device is proximate the location.
 3. The method of claim 2,wherein the step of affixing a token adjacent to the location comprisesthe step of affixing at least one of: (a) a token including a radiofrequency transponder that is excited by radio frequency energy emittedby the portable device, producing an altered radio frequency signal thatis detected by the portable device; (b) a token providing a pattern ofmagnetic flux, wherein the portable device detects the pattern ofmagnetic flux from the token to produce a signal indicative of aspecific type of component associated with the token; and (c) a tokenincluding an optical pattern, wherein the portable device detects theoptical pattern of a token to produce a signal indicative of a specifictype of component associated with the token.
 4. The method of claim 2,further comprising the step of logically coupling the token to the datacollection device, such that when the operator moves the portable deviceproximate the token, the portable device automatically produces therecord and stores the ancillary data.
 5. The method of claim 4, whereinthe step of logically coupling the token to the data collection devicecomprises the step of coupling the token to at least one of: (a) anodometer; (b) an hour meter; (c) a brake condition sensor; (d) an enginesensor; (e) a temperature sensor; (f) a pressure sensor; and (g) aposition sensor.
 6. The method of claim 2, further comprising the stepof affixing a plurality of tokens adjacent to a corresponding pluralityof other locations that are to be visited during the inspection, each ofthe plurality of tokens being associated with and affixed adjacent to adifferent one of the plurality of other locations and causing theportable device to detect when it is proximate the other locationassociated with the token, to identify said other location, producingthe record indicating that the operator was sufficiently close to theother location to perform an inspection at the other location.
 7. Themethod of claim 1, wherein the ancillary data relates to at least oneof: (a) an odometer reading; (b) an hour meter reading; (c) a brakecondition; (d) an engine condition; (e) a temperature; (f) a pressure;and (g) a geographical position.
 8. The method of claim 1, furthercomprising the step of transferring the record and the ancillary datafrom the portable device to a storage that is separate from the portabledevice.
 9. A method for using a portable device for collecting ancillarydata that include data values of interest and indicate that a locationwas visited during an inspection, comprising the steps of: (a) providinga portable device for use in recording ancillary data related to theinspection, said portable device being capable of receiving theancillary data from a data collection device that is disposed proximatethe location, only when the portable device is also disposed proximatethe location, the ancillary data having been collected by the datacollection device; and (b) enabling an operator to move the portabledevice proximate the location, such that the portable deviceautomatically interrogates the data collection device, causing theancillary data to be transferred to the portable device and therebyproviding evidence that the operator was sufficiently close to thelocation to perform the inspection at the location.
 10. The method ofclaim 9, wherein the step of enabling the operator to move the portabledevice proximate the location comprises the step of automaticallytransferring ancillary data to the portable device relating to at leastone of: (a) an odometer reading; (b) an hour meter reading; (c) a brakecondition; (d) an engine condition; (e) a temperature; (f) a pressure;and (g) a geographical position.
 11. The method of claim 9, furthercomprising the step of transferring the ancillary data from the portabledevice to a storage that is separate from the portable device.
 12. Themethod of claim 9, further comprising the step of logically coupling thedata collection device configured to collect the ancillary data to atleast one of: (a) an odometer; (b) an hour meter; (c) a brake conditionsensor; (d) an engine sensor; (e) a temperature sensor; (f) a pressuresensor; and (g) a position sensor.
 13. The method of claim 9, furthercomprising the step of positioning the data collection device proximatethe location before the inspection, the data collection device beingcoupled to a data transfer device to transfer the ancillary data to theportable device when interrogated, the data transfer device comprisingat least one of: (a) a radio frequency transponder that is excited byradio frequency energy emitted by the portable device, producing analtered radio frequency signal that is detected by the portable device;(b) a token providing a pattern of magnetic flux, wherein the portabledevice detects the pattern of magnetic flux provided by the token toidentify a specific type of component associated with the token; and (c)an optically readable token having an optical pattern, wherein theportable device detects the optical pattern to produce a signalindicative of a specific type of component associated with the opticallyreadable token.
 14. The method of claim 13, further comprising the stepof affixing a plurality of data transfer devices adjacent to acorresponding plurality of other locations that are to be visited duringthe inspection, each of the plurality of data transfer devices beingassociated with and affixed adjacent to a different one of the pluralityof other locations, each data transfer device being configured totransfer at least one type of ancillary data collected by a datacollection device with which the data transfer device is coupled andidentification data to the portable device when the portable device isproximate the other location associated with the data transfer device toidentify the other location, such that the at least one type ofancillary data and identification data received by the portable devicewhile proximate to the other location provides evidence that theoperator was sufficiently close to the other location to perform theinspection at the other location.
 15. A system for providing evidencethat a plurality of locations were visited during an inspection,comprising: (a) a plurality of tokens, each token being associated witha different location that is to be visited during the inspection andaffixed adjacent to the location, each token being configured to provideat least one of unique identification data that uniquely identifies thetoken, and at least one of the tokens being adapted to transferancillary data that have been collected by a data collection device towhich the token is adapted to be coupled; and (b) a portable deviceadapted to be transported to each location to be visited and inspectedduring the inspection, said portable device including: (i) a housing;(ii) a memory in which machine instructions and data are stored; (iii) asensor for detecting when the portable device is proximate each of theplurality of tokens, and thus within a predetermined maximum distancefrom each of the locations associated with the plurality of tokens, saidsensor producing a signal indicating when the portable device is withinthe predetermined maximum distance from any of the locations; (iv) areader configured to collect ancillary data when the portable device isproximate any of the plurality of tokens that are coupled to a datacollection device, and thus within the predetermined maximum distancefrom the location associated with the token, the reader responding tothe signal that is produced by the sensor, by receiving the ancillarydata from the token; and (v) a controller coupled to the memory, thereader, and the sensor, said controller executing the machineinstructions and, in response to the signal produced by the sensor,causing the memory to store data indicative of each location visitedduring the safety inspection, the stored data comprising the uniqueidentification data and any ancillary data transferred from the token atthe location.
 16. The system of claim 15, wherein the sensor and readerare implemented as a single component.
 17. The system of claim 16,wherein the single component comprises a radio frequency receiver.
 18. Asystem for providing evidence that a plurality of locations were visitedduring an inspection, comprising: (a) a plurality of tokens, each tokenbeing associated with a different location that is to be visited duringthe inspection and affixed adjacent to the location, each token beingconfigured to convey ancillary data collected by a data collectiondevice adapted to be coupled to the token, the ancillary data conveyedby each token being uniquely discriminable and associated with only oneof the plurality of locations to be inspected with which the token isassociated; and (b) a portable device adapted to be transported to eachlocation to be visited and inspected during the inspection, saidportable device including: (i) a housing; (ii) a memory in which machineinstructions and data are stored; (iii) a reader configured to collectancillary data conveyed by any of the plurality of tokens when theportable device is proximate the token, and thus within a predeterminedmaximum distance from the location with which the token is associated,the reader receiving the ancillary data, said ancillary data beingindicative that the portable device is within the predetermined maximumdistance from said location; and (iv) a controller coupled to thememory, the reader, and the sensor, said controller executing themachine instructions and, in response to the signal produced by thesensor, causing the memory to store the ancillary data that areindicative of each location visited during the inspection, as theancillary data for the location are collected by the reader.